Apache ActiveMQ ™ -- LDAP Broker Discovery Mechanism
Using ActiveMQ 5 > LDAP Broker Discovery Mechanism
Configuring network topologies can be quite tedious when the number of brokers in the system is large. To help ease the configuration overhead for these types of situations, a broker can be configured to look up its broker connections using a LDAP v3 directory server.
Note
The basic feature was added to satisfy AMQ-358. There are known problems and limitations with this implementation. These deficiencies have been addressed in AMQ-1587. The features discussed on this page require the patch attached to JIRA issue AMQ-1587. This patch should apply cleanly to the ActiveMQ 5.0.0 release or the current development trunk.
LDAP v3 Directory Server Compliance
The following table lists a known subset of directory servers and their compliance to work with the LDAP discovery feature. Most LDAP v3 directory servers will support this feature if they properly implement the RFC2307 schemas. In order to support the persistent search capabilities the server must implement the extension defined in draft-ietf-ldapext-psearch-03.txt.
Vendor
Product
Version
draft-ietf-ldapext-psearch-03.txt
Apache
ApacheDS
1.0.x
Microsoft
Active Directory
Windows 2000
Windows 2003
Microsoft
Active Directory
Windows 2003 R2
Sun
OpenDS
0.9.x
OpenLDAP
OpenLDAP
2.3.x
2.4.x
LDAP v3 directory server which do not support RFC2307 by default. Support can be added by manually importing them. See vendor specific setup requirements on how to do this. LDAP v3 directory servers which do not support the draft-ietf-ldapext-psearch-03.txt.
LDAP Network Connector Properties
Property
Default
Required
Description
uri
null
Yes
The URI of the LDAP v3 Server to connect to (i.e. ldap://host:port, failover://(ldap://host1:port,ldap://host2:port).
base
null
Yes
The RDN base used as the root for the search criteria.
user
null
Yes, if not using anonymousAuthentication
The username needed to bind to the server.
password
null
Yes, if not using anonymousAuthentication
The password needed to bind to the server.
anonymousAuthentication
false
Yes, if not using user/password
Enable if you want to bind to the server anonymously. This is recommended over using user/password properties since your login credentials will not be stored in an unencrypted XML file.
searchEventListener
false
No
Enable if you want the broker to stay in sync with changes made to entries matching the search criteria.
searchScope
ONELEVEL_SCOPE
No
Can be any of search scopes defined by javax.naming.directory.SearchControls class.
OBJECT_SCOPE - search the named object defined by base.
ONELEVEL_SCOPE - search one level of the base.
SUBTREE_SCOPE - search entire subtree rooted at the base.
searchFilter
(&(objectClass=ipHost)(objectClass=ipService))
No
Can be any filter that conforms to RFC2254. If a custom one is specified the actual search filter used will be (&(&(objectClass=ipHost)(objectClass=ipService))(USER CUSTOM))
Other Properties
All of the properties defined in Networks of Brokers are also available to the ldapNetworkConnector. Any of the properties defined for a normal networkConnector will be used as connection parameters to any discovered brokers matching the search criteria.
Example 1: Simple Network of Brokers
Network Configuration
Topology
LDAP v3 Directory Structure
Entry
ActiveMQ Configuration (activemq.xml)
srv-a.mydomain.com
srv-b.mydomain.com
Example 2: Larger Network of Brokers
Network Configuration
Topology
LDAP v3 Directory Structure
ActiveMQ Configuration (activemq.xml)
srv-a.mydomain.com
srv-b.mydomain.com
srv-c.mydomain.com
srv-d.mydomain.com